Skip to content

Remove err_depth #12167

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jun 17, 2025
Merged

Remove err_depth #12167

merged 6 commits into from
Jun 17, 2025

Conversation

Simn
Copy link
Member

@Simn Simn commented Apr 12, 2025

I don't understand why we would want to track this manually. The depth of an error should at all times be derived from the error's structure, and I don't see why we would ever want to raise an error with depth != 0.

@Simn
Copy link
Member Author

Simn commented Apr 19, 2025

@kLabz Would be good to check this soon because it's a bit conflict-prone.

@kLabz
Copy link
Contributor

kLabz commented May 6, 2025

Sorry, was not around. This was mostly added because there were still many cases where sub errors were not added as such, will check if there's any left after this.

@kLabz
Copy link
Contributor

kLabz commented May 12, 2025

Looks good 👍

However now depth arguments are ignored in haxe.macro.Context API (but still exist, which is easy enough to "fix"), without providing any alternative. Ideally, Context.error, Context.fatalError and Context.reportError would let users define sub errors too.

(also ideally, depth would be removed from warning/info too and "sub" items would be added there instead too)

@kLabz kLabz merged commit b6a2db6 into development Jun 17, 2025
93 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants